This pull request has been marked 'stale' due to lack of recent activity. If there is no further activity, the PR will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark pull requests as stale.

Rather, unless something is breaking stability (e.g. a project I maintain won't install anymore, or breaks completely and CI blows up), or there's a major feature or missing component that I agree would be a no-brainer to have incorporated

I reckon this is a no-brainer.

This issue is no longer marked for closure.

@geerlingguy any chance of this being merged?

The biggest use case for this is we can put it onto a separate volume than root without having all of /var in a separate disk in AWS.

I've tested this and it works well just by setting this in the config/vars:

postgresql_data_dir: "/data/pgsql/{{ postgresql_version }}/data"

Much easier to move the data to another mounted volume

This pull request has been marked 'stale' due to lack of recent activity. If there is no further activity, the PR will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark pull requests as stale.

Still not stale :)

This issue is no longer marked for closure.

This pull request has been marked 'stale' due to lack of recent activity. If there is no further activity, the PR will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark pull requests as stale.

This issue is no longer marked for closure.

I ended up adding a custom data directory to the molecule tests, which is why everything else is failing in the PR.

What would be the best way to handle the __postgresql_config_path: "/var/lib/pgsql/data" that won't exist if you use a custom directory? Would it make sense to have __postgresql_config_path: be __postgresql_config_path: "{{ postgresql_data_dir }}"?

This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

no stale

So it's failing on the EL versions because __postgresql_config_path is defaulting to the old data directory I believe?

Is there a way in molecule to have specific variables for the different distros?

This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.